Skip to content

v6: docs: fix typos, examples, and utility class docs#42430

Open
coliff wants to merge 2 commits into
twbs:v6-devfrom
coliff:dev/coliff/v6-docs-updates
Open

v6: docs: fix typos, examples, and utility class docs#42430
coliff wants to merge 2 commits into
twbs:v6-devfrom
coliff:dev/coliff/v6-docs-updates

Conversation

@coliff
Copy link
Copy Markdown
Contributor

@coliff coliff commented May 23, 2026

Description

Minor documentation fixes across multiple site files:

  • examples/sign-in: add meaningful alt text for the logo image for accessibility.
  • components/dialog: add missing space in example button markup.
  • for shared property-value pairs: update navbar example to use new prefix-style responsive class (.{breakpoint}:navbar-expand).
  • forms/layout: update horizontal form docs to recommend .{breakpoint}:col-* usage.
  • getting-started/approach: fix grammar/typos, correct docsref path, and clarify component modifier/variant naming (mention .btn-solid and .theme-primary).
  • getting-started/javascript: adjust JS-required components list (add Dialog, remove Accordions/Modals lines).
  • guides/migration: fix possessive "its" typos in breakpoint/container notes.
  • helpers/stretched-link: correct placeholder title text.
  • utilities/background: update example to use fg-contrast-{name} / fg-{name} classes instead of previous color-* naming.

Motivation & Context

These changes improve clarity, accessibility, and align docs with updated class naming conventions.

Type of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (non-breaking change)
  • Breaking change (fix or feature that would change existing functionality)

Checklist

  • I have read the contributing guidelines
  • My code follows the code style of the project (using npm run lint)
  • My change introduces changes to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed

Live previews

Related issues

Copilot AI review requested due to automatic review settings May 23, 2026 01:12
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Docs-focused PR to align examples and guidance with Bootstrap 6’s updated theming tokens, responsive class prefixing, and to clean up minor typos/accessibility issues.

Changes:

  • Updated utility/component examples to use new fg-*/fg-contrast-* and responsive .{breakpoint}:* class patterns.
  • Corrected typos/grammar and fixed a malformed attribute spacing in a dialog example.
  • Improved example accessibility by adding alt text to the Bootstrap logo image.

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
site/src/content/docs/utilities/background.mdx Updates background utility examples to new foreground utility classes.
site/src/content/docs/helpers/stretched-link.mdx Fixes placeholder title text typo in example markup.
site/src/content/docs/guides/migration.mdx Fixes “it’s” → “its” grammar in breakpoint migration notes.
site/src/content/docs/getting-started/javascript.mdx Updates JS-required components list to include Dialog (and removes a couple prior entries).
site/src/content/docs/getting-started/approach.mdx Fixes wording and updates selector/theming guidance and a docsref link.
site/src/content/docs/forms/layout.mdx Updates horizontal form guidance to new responsive class syntax.
site/src/content/docs/components/navbar.mdx Updates navbar expand class guidance to new responsive prefix syntax.
site/src/content/docs/components/dialog.mdx Fixes missing whitespace in button example attributes.
site/src/assets/examples/sign-in/index.astro Adds alt text to the Bootstrap logo in the sign-in example.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Aside from [Reboot]([[docsref:/content/reboot]]), we strive to use only classes as selectors. Where we can, we avoid type selectors and extraneous parent selectors for greater flexibility.

Components are typically built with a base class for shared property-value pairs. For example, `.btn` and `.btn-primary`. We use `.btn` for all the common styles like `display`, `padding`, and `border-width`. We then use modifiers like `.btn-solid` to add more styles.
Components are typically built with a base class for shared property-value pairs. For example, `.btn`, `.btn-solid`, and `.theme-primary`. We use `.btn` for all the common styles like `display`, `padding`, and `border-width`. We then use variant and theme modifiers like `.btn-solid.theme-primary` to add more styles.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph probably needs an update because buttons now don't need a base class for shared property-value pairs so the first sentence in the diff above is not correct for buttons.

Comment thread site/src/assets/examples/sign-in/index.astro
@mdo
Copy link
Copy Markdown
Member

mdo commented May 28, 2026

Was this a bad rebase? Seeing some dependabot and @julien-deramond commits?

@julien-deramond
Copy link
Copy Markdown
Member

Was this a bad rebase? Seeing some dependabot and @julien-deramond commits?

I don't want to mess with the branch, not knowing exactly what's inside and what's the status, but locally, if I do:

git fetch -p origin
gh pr checkout 42430
git rebase -i origin/v6-dev

I got

warning: skipped previously applied commit d0a148e96
warning: skipped previously applied commit 38e8f2588
warning: skipped previously applied commit b766b7e11
warning: skipped previously applied commit 39026aac2
warning: skipped previously applied commit f7837487f
warning: skipped previously applied commit 9a5728a8d
warning: skipped previously applied commit 051635822

And only 3 commits authored by Christian in the end.

So I'd say it'd just need to be rebased again after the recent changes in v6-dev, yeah.

@coliff coliff force-pushed the dev/coliff/v6-docs-updates branch from 71371c4 to 8ffa0be Compare May 28, 2026 05:05
coliff added 2 commits May 28, 2026 14:06
Minor documentation fixes across multiple site files:

- examples/sign-in: add meaningful alt text for the logo image for accessibility.
- components/dialog: add missing space in example button markup.
- components/navbar: update navbar example to use new prefix-style responsive class (`.{breakpoint}:navbar-expand`).
- forms/layout: update horizontal form docs to recommend `.{breakpoint}:col-*` usage.
- getting-started/approach: fix grammar/typos, correct docsref path, and clarify component modifier/variant naming (mention `.btn-solid` and `.theme-primary`).
- getting-started/javascript: adjust JS-required components list (add Dialog, remove Accordions/Modals lines).
- guides/migration: fix possessive "its" typos in breakpoint/container notes.
- helpers/stretched-link: correct placeholder title text.
- utilities/background: update example to use `fg-contrast-{name}` / `fg-{name}` classes instead of previous `color-*` naming.

These changes improve clarity, accessibility, and align docs with updated class naming conventions.
text would always be white on black background
Update example code for background gradient usage
Update margin utilities docs for v6 spacers
Docs updated to reflect the v6 spacing scale: sizes now range from 0 through 9 (`.m-0`–`.m-9`) and the multiplier values for sizes 3–9 were adjusted.

Negative margin docs were changed to note that v6 only supports negative inline margins (`.ms--1`, `.me--2`) using `-1` and `-2` spacers and that the v5-style full negative utilities (e.g. `.mt-n1`) were removed.

The responsive examples were updated to list `.{breakpoint}m-0` through `.{breakpoint}m-9` and `.{breakpoint}m-auto`.
@coliff coliff force-pushed the dev/coliff/v6-docs-updates branch from 8ffa0be to 4cff922 Compare May 28, 2026 05:07
@coliff
Copy link
Copy Markdown
Contributor Author

coliff commented May 28, 2026

sorry 'bout that. I think it's all good now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants